MkPullRequestGuidelines
Node showing pull request guidelines.¶
Bases: MkTemplate
| Name | Children | Inherits |
|---|---|---|
| MkTemplate mknodes.templatenodes.mktemplate Node representing a jinja template. |
graph TD
94396150417776["mkpullrequestguidelines.MkPullRequestGuidelines"]
94396150980560["mktemplate.MkTemplate"]
94396150332256["mkcontainer.MkContainer"]
94396150626816["mknode.MkNode"]
94396150902384["node.Node"]
140181802719712["builtins.object"]
94396150980560 --> 94396150417776
94396150332256 --> 94396150980560
94396150626816 --> 94396150332256
94396150902384 --> 94396150626816
140181802719712 --> 94396150902384
/home/runner/work/mknodes/mknodes/mknodes/templatenodes/mkpullrequestguidelines/metadata.toml
[metadata]
name = "MkPullRequestGuidelines"
icon = "octicon:git-pull-request-24"
group = "documentation"
# [examples.regular]
# title = "Regular"
# jinja = """
# {{ mk.MkPullRequestGuidelines() }}
# """
[output.markdown]
template = """
Link to any related issue in the Pull Request message.
During the review, we recommend using fixups:
{{ "git commit --fixup=SHA # SHA of commit you want to fix" | MkCode }}
Once all the changes are approved, you can squash your commits:
{{ "git rebase -i --autosquash main" | MkCode }}
And force-push:
{{ "git push -f" | MkCode }}
If this seems all too complicated, you can push or force-push each new commit,
and we will squash them ourselves if needed, before merging.
"""